home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19981211-19990422
/
000331_news@watsun.cc.columbia.edu _Mon Mar 8 03:05:47 1999.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Return-Path: <news@watsun.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id DAA25622
for <kermit.misc@watsun.cc.columbia.edu>; Mon, 8 Mar 1999 03:05:41 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id CAA13958
for kermit.misc@watsun.cc.columbia.edu; Mon, 8 Mar 1999 02:40:14 -0500 (EST)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: vek@pharmnl.ohout.pharmapartners.nl (Villy Kruse)
Subject: Re: kermit messages
Date: 8 Mar 1999 08:39:35 +0100
Organization: A poorly-installed InterNetNews site
Message-ID: <7bvurn$fto$1@pharmnl.ohout.pharmapartners.nl>
To: kermit.misc@mailrelay2.cc.columbia.edu
In article <7bsdsg$epk$1@newsmaster.cc.columbia.edu>,
Frank da Cruz <fdc@watsun.cc.columbia.edu> wrote:
>In article <y93ogm6mcry.fsf@zohar.ai.mit.edu>,
>Allan Adler <ara@zohar.ai.mit.edu> wrote:
>: Today I started getting
>: a new message in addition to the overrun message. It is:
>:
>: ll_rw_block: device 03:02: only 1024-char blocks implemented (4096)
>:
>: ................snip
>:
>Which version of C-Kermit are you using? Newer versions do bigger disk
>writes. Version 7.0 might try to write anywhere from 4K to 32K at a time.
>Evidently your disk device driver doesn't handle large writes "atomically"
>and therefore puts up a warning message to let you know this. But from what
>you said, it also appears to recover from them by breaking large writes up
>into smaller ones internally.
This messages (ll_rw_block: ..etc...) is totally unrelated to kermit.
It could be related to some strange IDE disk drive being used as a
swap device.
Device 03:02 is translated into /dev/hda2 with the major and minor
device numbers being 3 and 2 respectively. As long as we don't know
how /dev/hda2 is used we cannot guess on the reason for the ll_rw_block
message.
Kermit writes of whatever block size goes to the file system which will
do its magic before putting the data on the disk.
Villy